Skip to content

Document agentless Feature Flags delivery for Node.js#38231

Open
leoromanovsky wants to merge 17 commits into
masterfrom
leo.romanovsky/agentless-feature-flags-docs
Open

Document agentless Feature Flags delivery for Node.js#38231
leoromanovsky wants to merge 17 commits into
masterfrom
leo.romanovsky/agentless-feature-flags-docs

Conversation

@leoromanovsky

@leoromanovsky leoromanovsky commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Motivation

The upcoming Node.js Feature Flags releases add a Datadog-managed CDN configuration source that does not require a Datadog Agent. The documentation currently presents Agent Remote Configuration as the server SDK delivery path and describes no-Agent serverless delivery as unsupported.

Customers need the new default explained before adopting the releases, including exact minimum versions and the initial limitation that no-Agent deployments do not deliver exposure or aggregate flagevaluation events.

Related implementation: DataDog/dd-trace-js#9397

Changes

  • Add a Server SDK Configuration Sources concept page and surface it in the Server SDK navigation.
  • Revise the Server SDK overview and serverless guidance to present agentless configuration delivery as the default for supported Node.js versions.
  • Document the held release minimums: Node.js v5 5.116.0 and Node.js v6 6.5.0.
  • Add agentless and explicit Agent Remote Configuration setup details to the Node.js page.
  • Keep Java and other server SDKs on their existing Agent Remote Configuration documentation.
  • State consistently that the initial Node.js agentless releases support configuration delivery and local flag evaluation, but not agentless exposure or aggregate flagevaluation event delivery.

Input needed from reviewers

  • The code snippets have been extensively validated; your 2nd pass is appreciated.
    *** Presenting the information in parallel with RC and the organization is the principal help needed.**

@github-actions github-actions Bot added the Architecture Everything related to the Doc backend label Jul 16, 2026
@datadog-datadog-us1-prod

This comment has been minimized.

@leoromanovsky leoromanovsky changed the title Document agentless Feature Flags delivery for Java and Node.js Document agentless Feature Flags delivery for Node.js Jul 22, 2026
@github-actions github-actions Bot added the Guide Content impacting a guide label Jul 22, 2026
@leoromanovsky

Copy link
Copy Markdown
Contributor Author

/review

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Automated review by Claude. AI-generated; verify before acting.

Style and consistency findings only — no blockers. New page is well-structured and adds needed content. Main issues: inconsistent capitalization of the product name Remote Configuration in several headings, capitalization of "agentless" in headings, an em-dash formatting mismatch, one ambiguous reference to a future release, and a potentially confusing "Node.js 5.116.0" (this is a dd-trace version, not a Node.js runtime version).

Reviewed 558b4e2bd7793fe98b55094028af52db9c25b5d9workflow run

Comment thread content/en/feature_flags/_index.md Outdated
Comment thread content/en/feature_flags/concepts/configuration_sources.md Outdated
Comment thread content/en/feature_flags/concepts/configuration_sources.md Outdated
Comment thread content/en/feature_flags/concepts/configuration_sources.md Outdated
Comment thread content/en/feature_flags/concepts/configuration_sources.md Outdated
Comment thread content/en/feature_flags/server/_index.md Outdated
Comment thread content/en/feature_flags/server/_index.md Outdated
Comment thread content/en/feature_flags/server/nodejs.md Outdated
Comment thread content/en/feature_flags/server/nodejs.md Outdated
Comment thread content/en/feature_flags/implementation_patterns/serverless.md Outdated
Comment thread content/en/feature_flags/concepts/configuration_sources.md Outdated
Comment thread content/en/feature_flags/concepts/configuration_sources.md Outdated
Comment thread content/en/feature_flags/concepts/configuration_sources.md Outdated
Comment thread content/en/feature_flags/implementation_patterns/serverless.md Outdated
Comment thread content/en/feature_flags/implementation_patterns/serverless.md Outdated
Comment thread content/en/feature_flags/implementation_patterns/serverless.md Outdated
Comment thread content/en/feature_flags/implementation_patterns/serverless.md Outdated
Comment thread content/en/feature_flags/server/_index.md Outdated
Comment thread content/en/feature_flags/server/nodejs.md Outdated
@leoromanovsky

Copy link
Copy Markdown
Contributor Author

/review

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Automated review by Claude. AI-generated; verify before acting.

Content is well-structured and clearly explains the new agentless delivery mode. A few small issues: two unused reference-link definitions, one hyphenation inconsistency with feature_flags/_index.md, and a couple of clarity nits.

Reviewed b18c59f489aadfdff1a4e279836605130e5dc967workflow run

Comment thread content/en/feature_flags/server/nodejs.md Outdated
Comment thread content/en/feature_flags/server/_index.md Outdated
Comment thread content/en/feature_flags/server/_index.md
Comment thread content/en/feature_flags/concepts/configuration_sources.md Outdated
Comment thread content/en/feature_flags/implementation_patterns/serverless.md
Comment thread content/en/feature_flags/concepts/configuration_sources.md Outdated
@leoromanovsky
leoromanovsky marked this pull request as ready for review July 22, 2026 16:46
@leoromanovsky
leoromanovsky requested a review from a team as a code owner July 22, 2026 16:46
@leoromanovsky
leoromanovsky requested a review from aarsilv July 22, 2026 16:46
@joepeeples joepeeples added the editorial review Waiting on a more in-depth review label Jul 22, 2026
@joepeeples

Copy link
Copy Markdown
Contributor

Opened DOCS-15171 to follow up with editorial review.

@aarsilv aarsilv left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving with some minor suggestions about changes that happened while pairing. I'll submit a commit that updates.

Comment thread content/en/feature_flags/concepts/configuration_sources.md
Comment thread content/en/feature_flags/concepts/configuration_sources.md
Comment thread content/en/feature_flags/concepts/configuration_sources.md
Comment thread content/en/feature_flags/concepts/configuration_sources.md
Comment thread content/en/feature_flags/concepts/configuration_sources.md
Comment thread content/en/feature_flags/concepts/configuration_sources.md Outdated
@leoromanovsky

Copy link
Copy Markdown
Contributor Author

Approving with some minor suggestions about changes that happened while pairing. I'll submit a commit that updates.

@aarsilv I wrote this document taking into account two commits now in review and the decisions I made with Ruben assuming they would land and are part of the specification. Please take a read of them and review whether the documentation still matches.

aarsilv and others added 3 commits July 22, 2026 23:49
Document that the SDK sends the DD-API-KEY header to custom endpoints and that HTTP is permitted only for loopback hosts, matching shipped dd-trace 5.116.0/6.5.0 behavior.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Restores content/en/feature_flags/concepts/configuration_sources.md and content/en/feature_flags/server/nodejs.md to their state before a45a054.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

@joepeeples joepeeples left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exciting new content, thanks @leoromanovsky for adding it! In addition to some line-edit suggestions, I think we could reorder the sections on the new Configuration Sources page for a clearer information architecture.

Because there are two major config source options, I'd expect them to be on more equal footing (even if one is default in some cases). But Remote Config is buried under "Advanced configuration," which also has agentless stuff mixed in, too. Here's a possible reorg, to have two major sections for the config options, and another section grouping topics that are common to both config options:

Server SDK Configuration Sources - overview
- Choose a configuration source
- Use agentless delivery (fka "Get started with agentless")
	- Configure agentless delivery
	- Use a custom agentless endpoint
	- Migrate an existing Remote Configuration setup
- Use Agent Remote Configuration
- Advanced configuration
	- Enable or disable flags
	- Activation and billing
	- Configuration precedence

Let me know if you think this would work, or if we should organize in a different direction.

Comment thread content/en/feature_flags/guide/server_flag_evaluation_metrics.md Outdated
Comment thread content/en/feature_flags/server/_index.md Outdated
Comment thread content/en/feature_flags/server/_index.md Outdated
Comment thread content/en/feature_flags/server/_index.md Outdated
Comment thread content/en/feature_flags/server/_index.md Outdated
Comment thread content/en/feature_flags/concepts/configuration_sources.md Outdated
Comment thread content/en/feature_flags/implementation_patterns/serverless.md Outdated
Comment thread content/en/feature_flags/server/_index.md
Comment thread content/en/feature_flags/server/nodejs.md Outdated
Comment thread content/en/feature_flags/server/nodejs.md Outdated
Co-authored-by: Joe Peeples <joe.peeples@datadoghq.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Architecture Everything related to the Doc backend editorial review Waiting on a more in-depth review Guide Content impacting a guide

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants